P4c was written and not applied. The runs then demonstrated why it
matters: root-cause-validation failed only on "offers the choice and
waits" and "announces that validation is running", and
implementation-picks-first-task came back FLAKY on "asks the question,
gathering the answer" — evidenced in one run's narrative, absent from
the other, with an identical world both times. Display claims don't
merely fail; they fail intermittently, which is worse than failing.

Each is rewritten as something the record can prove:

- "offers the choice and waits" → the scripted yes was consumed, so the
  run arm was taken; a skip would have returned with no dispatch
- "announces running, dispatches exactly one agent" → one dispatch
  recorded, one report written, no second of either
- "asks the question, gathering without acting" → the answer was
  consumed there, and no setup document was written or committed by the
  entry
- "renders the phase note and emits it as produced" → renders it through
  the engine with the verb Starting; the render is an engine call, the
  emission is not

No prose touched — this is test authoring only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>